Cell Magics in IPython

IPython has a system of commands we call 'magics' that provide effectively a mini command language that is orthogonal to the syntax of Python and is extensible by the user with new commands. Magics are meant to be typed interactively, so they use command-line conventions, such as using whitespace for separating arguments, dashes for options and other conventions typical of a command-line environment.

Magics come in two kinds:

Line magics: these are commands prepended by one % character and whose arguments only extend to the end of the current line.
Cell magics: these use two percent characters as a marker (%%), and they receive as argument both the current line where they are declared and the whole body of the cell. Note that cell magics can only be used as the first line in a cell, and as a general principle they can't be 'stacked' (i.e. you can only use one cell magic per cell). A few of them, because of how they operate, can be stacked, but that is something you will discover on a case by case basis.

The %lsmagic magic is used to list all available magics, and it will show both line and cell magics currently defined:



In [1]:

    
%lsmagic









    Out[1]:





Available line magics:
%alias  %alias_magic  %autocall  %automagic  %autosave  %bookmark  %cd  %clear  %colors  %config  %connect_info  %debug  %dhist  %dirs  %doctest_mode  %ed  %edit  %env  %gist  %gui  %hist  %history  %install_default_config  %install_ext  %install_profiles  %killbgscripts  %less  %load  %load_ext  %loadpy  %logoff  %logon  %logstart  %logstate  %logstop  %lsmagic  %macro  %magic  %man  %matplotlib  %more  %notebook  %page  %pastebin  %pdb  %pdef  %pdoc  %pfile  %pinfo  %pinfo2  %popd  %pprint  %precision  %profile  %prun  %psearch  %psource  %pushd  %pwd  %pycat  %pylab  %qtconsole  %quickref  %recall  %rehashx  %reload_ext  %rep  %rerun  %reset  %reset_selective  %run  %save  %sc  %store  %sx  %system  %tb  %tic  %time  %timeit  %toc  %unalias  %unload_ext  %who  %who_ls  %whos  %xdel  %xmode

Available cell magics:
%%!  %%HTML  %%SVG  %%bash  %%capture  %%debug  %%file  %%html  %%javascript  %%latex  %%perl  %%prun  %%pypy  %%python  %%python3  %%ruby  %%script  %%sh  %%svg  %%sx  %%system  %%time  %%timeit  %%writefile

Automagic is ON, % prefix IS NOT needed for line magics.

Since in the introductory section we already covered the most frequently used line magics, we will focus here on the cell magics, which offer a great amount of power.

Let's load matplotlib and numpy so we can use numerics/plotting at will later on.



In [2]:

    
%matplotlib inline
import numpy as np
import matplotlib.pyplot as plt

Some simple cell magics

Timing the execution of code; the 'timeit' magic exists both in line and cell form:



In [3]:

    
%timeit np.linalg.eigvals(np.random.rand(100,100))









    



100 loops, best of 3: 6.05 ms per loop



In [4]:

    
%%timeit a = np.random.rand(100, 100)
np.linalg.eigvals(a)









    



100 loops, best of 3: 6.07 ms per loop

The %%capture magic can be used to capture the stdout/err of any block of python code, either to discard it (if it's noise to you) or to store it in a variable for later use:



In [5]:

    
%%capture capt
from __future__ import print_function
import sys
print('Hello stdout')
print('and stderr', file=sys.stderr)



In [6]:

    
capt.stdout, capt.stderr









    Out[6]:





('Hello stdout\n', 'and stderr\n')



In [7]:

    
capt.show()









    



Hello stdout






    



and stderr

The %%writefile magic is a very useful tool that writes the cell contents as a named file:



In [8]:

    
%%writefile foo.py
print('Hello world')









    



Writing foo.py



In [9]:

    
%run foo









    



Hello world

Magics for running code under other interpreters

IPython has a %%script cell magic, which lets you run a cell in a subprocess of any interpreter on your system, such as: bash, ruby, perl, zsh, R, etc.

It can even be a script of your own, which expects input on stdin.

To use it, simply pass a path or shell command to the program you want to run on the %%script line, and the rest of the cell will be run by that script, and stdout/err from the subprocess are captured and displayed.



In [10]:

    
%%script python
import sys
print 'hello from Python %s' % sys.version









    



hello from Python 2.7.2 (default, Oct 11 2012, 20:14:37) 
[GCC 4.2.1 Compatible Apple Clang 4.0 (tags/Apple/clang-418.0.60)]



In [11]:

    
%%script python3
import sys
print('hello from Python: %s' % sys.version)









    



hello from Python: 3.3.1 (v3.3.1:d9893d13c628, Apr  6 2013, 11:07:11) 
[GCC 4.2.1 (Apple Inc. build 5666) (dot 3)]

IPython also creates aliases for a few common interpreters, such as bash, ruby, perl, etc.

These are all equivalent to %%script <name>



In [12]:

    
%%ruby
puts "Hello from Ruby #{RUBY_VERSION}"









    



Hello from Ruby 1.9.3



In [13]:

    
%%bash
echo "hello from $BASH"









    



hello from /usr/local/bin/bash

Exercise: write your own script that numbers input lines

Write a file, called lnum.py, such that the following cell works as shown (hint: don't forget about the executable bit!):



In [29]:

    
%%script ./lnum.py
my first line
my second
more









    



0: my first line
1: my second
2: more
---- END ----

Capturing output

You can also capture stdout/err from these subprocesses into Python variables, instead of letting them go directly to stdout/err



In [30]:

    
%%bash
echo "hi, stdout"
echo "hello, stderr" >&2









    



hi, stdout






    



hello, stderr



In [31]:

    
%%bash --out output --err error
echo "hi, stdout"
echo "hello, stderr" >&2



In [32]:

    
print(error)
print(output)









    



hello, stderr

hi, stdout

Background Scripts

These scripts can be run in the background, by adding the --bg flag.

When you do this, output is discarded unless you use the --out/err flags to store output as above.



In [33]:

    
%%ruby --bg --out ruby_lines
for n in 1...10
    sleep 1
    puts "line #{n}"
    STDOUT.flush
end









    



Starting job # 0 in a separate thread.

When you do store output of a background thread, these are the stdout/err pipes, rather than the text of the output.



In [34]:

    
ruby_lines









    Out[34]:





<open file '<fdopen>', mode 'rb' at 0x112cd55d0>



In [35]:

    
print(ruby_lines.read())









    



line 1
line 2
line 3
line 4
line 5
line 6
line 7
line 8
line 9